Skip to content

Conversation

@koppor
Copy link
Member

@koppor koppor commented Jul 1, 2025

Fixes #13423

Follow-up to #13401

Mandatory checks

  • I own the copyright of the code submitted and I license it under the MIT license
  • [/] Change in CHANGELOG.md described in a way that is understandable for the average user (if change is visible to the user)
  • [/] Tests created for changes (if applicable)
  • [/] Manually tested changed features in running JabRef (always required)
  • [/] Screenshots added in PR description (if change is visible to the user)
  • [/] Checked developer's documentation: Is the information available and up to date? If not, I outlined it in this pull request.
  • [/] Checked documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request to the documentation repository.

@trag-bot
Copy link

trag-bot bot commented Jul 1, 2025

@trag-bot didn't find any issues in the code! ✅✨

@koppor
Copy link
Member Author

koppor commented Jul 1, 2025

@koppor koppor marked this pull request as ready for review July 1, 2025 18:31
@trag-bot
Copy link

trag-bot bot commented Jul 1, 2025

@trag-bot didn't find any issues in the code! ✅✨

@koppor koppor merged commit 9e5e5df into main Jul 1, 2025
2 checks passed
@koppor koppor deleted the fix-publishing branch July 1, 2025 18:32
@github-actions github-actions bot mentioned this pull request Jul 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix publication

2 participants